Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: Adjust migration variation and hook interaction #264

Merged
merged 2 commits into from
Apr 2, 2024

Conversation

keelerm84
Copy link
Member

@keelerm84 keelerm84 commented Mar 28, 2024

BEGIN_COMMIT_OVERRIDE
chore: Adjust migration variation and hook interaction #264
END_COMMIT_OVERRIDE

@keelerm84 keelerm84 requested a review from a team March 28, 2024 19:55
Copy link

This pull request has been linked to Shortcut Story #238448: Update otel work to handle migration method.

@keelerm84 keelerm84 merged commit c5a0e7a into feat/hooks Apr 2, 2024
1 check passed
@keelerm84 keelerm84 deleted the mk/sc-238448/migrations branch April 2, 2024 17:07
keelerm84 added a commit that referenced this pull request Apr 5, 2024
🤖 I have created a release *beep* *boop*
---

This release introduces a Hooks API. Hooks are collections of
user-defined callbacks that are executed by the SDK at various points of
interest. You can use them to augment the SDK with metrics or tracing.

##
[8.4.0](8.3.1...8.4.0)
(2024-04-05)


### Features

* Add initial support for hooks
([#256](#256))
([3cf16eb](3cf16eb))


### Bug Fixes

* Adjust migration variation and hook interaction
([#264](#264))
([8067af6](8067af6))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Matthew Keeler <mkeeler@launchdarkly.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants